Skip to content

Conversation

@justinmk3
Copy link
Contributor

Problem:
When debugging the extension, vscode tends to ignore the log-level that was set from the AWS Toolkit Logs UI.

Solution:
If the dev-mode aws.dev.logfile path is configured, log to it at "debug" log-level regardless of the (initial) vscode.LogOutputChannel.logLevel.


License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@justinmk3 justinmk3 requested a review from a team as a code owner October 10, 2024 21:06
@aws aws deleted a comment from github-actions bot Oct 10, 2024
@aws aws deleted a comment from github-actions bot Oct 10, 2024
Problem:
When debugging the extension, vscode tends to ignore the log-level that
was set from the `AWS Toolkit Logs` UI.

Solution:
If the dev-mode `aws.dev.logfile` path is configured, log to it at
"debug" log-level regardless of the (initial) `vscode.LogOutputChannel.logLevel`.
@aws aws deleted a comment from github-actions bot Oct 10, 2024
@justinmk3 justinmk3 merged commit edd90ca into aws:master Oct 10, 2024
21 of 24 checks passed
@justinmk3 justinmk3 deleted the minvscode branch October 10, 2024 21:52
tverney pushed a commit to tverney/aws-toolkit-vscode that referenced this pull request Oct 21, 2024
…s#5770

Problem:
When debugging the extension, vscode tends to ignore the log-level that
was set from the `AWS Toolkit Logs` UI.

Solution:
If the dev-mode `aws.dev.logfile` path is configured, log to it at
"debug" log-level regardless of the (initial)
`vscode.LogOutputChannel.logLevel`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant